Device enabled identification and authentication

ABSTRACT

Systems and methods that facilitate performing multiple transactions at once using a vehicle based wallet are disclosed herein. The vehicle based wallet can link to a plurality of mobile wallets and perform singular transactions with ATMs and POS machines, the singular transactions being a group transaction associated with one or more of the mobile wallets. The vehicle based wallet can collect intended transactions between the ATMs and the POS machines and the mobile wallets, and then gather them together and perform a single group transaction made up of the individual transactions for multiple people that are within the vehicle.

BACKGROUND

Automated teller machines (“ATMs”) and point of sale (“POS”) machinesperform transactions one at a time. If there are multiple people whowould like to perform a transaction, each person has to be verified,request a transaction and then complete the transaction. If a vehicledrives up to an ATM and more than one person wishes to perform atransaction then multiple transactions are required. Likewise, if thereare multiple people in a vehicle and they are splitting a transaction(such as a gas purchase or paying for tolls) there is no easy way forthe group to divide the payment besides exchanging cash with oneanother. This can lead to people tracking debts or can lead to longerwait times at the pumps or tolls while individuals in a single vehicledivide the cost amongst each other.

SUMMARY

The following presents a simplified summary in order to provide a basicunderstanding of some aspects of the innovation. This summary is not anextensive overview of the innovation. It is not intended to identifykey/critical elements or to delineate the scope of the innovation. Itssole purpose is to present some concepts of the innovation in asimplified form as a prelude to the more detailed description that ispresented later.

The disclosure disclosed and claimed herein, in one aspect thereof,includes systems and methods that facilitate performing multipletransactions at once using a vehicle based wallet. The vehicle basedwallet can link to a plurality of mobile wallets and perform singulartransactions with ATMs and POS machines, the singular transactions beinga group transaction associated with one or more of the mobile wallets.The vehicle based wallet can collect intended transactions between theATMs and the POS machines and the mobile wallets, and then gather themtogether and perform a single group transaction made up of theindividual transactions for multiple people that are within the vehicle.

In an embodiment, the vehicle based wallet system can verify each of themobile devices connecting to the vehicle based wallet system by havingeach of the mobile devices enter a code, unique to each user, or uniqueto the vehicle, into their mobile devices. The mobile devices can alsobe verified using GPS or other location data, by matching the locationor verifying the proximity between the mobile devices and the vehiclebased wallet system. The electronic connection between the vehicle basedwallet system and the ATM or POS machine can also be verified byentering one or more codes in either the ATM/POS or a device associatedwith the vehicle based wallet system (e.g, one of the mobile devices, oranother device in the vehicle). Location information can also beverified by determining whether the vehicle based wallet system andvehicle are near the ATM/POS machine, or are within a predetermineddistance.

For these considerations, as well as other considerations, in one ormore embodiments, a vehicle based wallet system can include a memory tostore computer-executable instructions and a processor, coupled to thememory, to facilitate execution of the computer-executable instructionsto perform operations. The operations can include receiving walletregistration data from a plurality of mobile devices, wherein the walletregistration data includes financial account data and security data. Theoperations can also include verifying the wallet registration data forthe plurality of mobile devices and compiling transaction dataassociated with a set of transactions from the plurality of mobiledevices and transmitting the transaction data to a financial transactiondevice. The operations can also include adjusting a vehicle walletbalance in response to receiving a notification that the financialtransaction device has processed the set of transactions associated withthe transaction data, wherein the adjusting the vehicle wallet balancecomprises adjusting a set of wallets associated with each of theplurality of mobile devices.

In another embodiment, a method includes registering, by a devicecomprising a processor, a set of mobile wallets with a vehicle basedwallet, wherein the registering comprises collecting financial accountdata and security data associated with the set of mobile wallets, andwherein the set of mobile wallets are associated with a set ofcorresponding mobile devices. The method also includes verifying the setof mobile wallets by matching a location of the set of mobile devices toa location of the of the vehicle based wallet and collecting transactiondata associated with a set of transactions from the mobile wallets. Themethod also includes transmitting the transaction data to a financialtransaction device and adjusting a balance of the vehicle based walletin response to receiving a notification that the financial transactiondevice has processed the set of transactions associated with thetransaction data.

In another embodiment, a non-transitory computer-readable mediumconfigured to store instructions, that when executed by a processorperform operations including, receiving wallet registration data from aplurality of mobile devices, wherein the wallet registration dataincludes financial account data and security data and verifying thewallet registration data for the plurality of mobile devices by matchinglocations associated with the plurality of mobile devices to a locationassociated with a vehicle based wallet device. The operations can alsoinclude compiling transaction data associated with a set of transactionsfrom the plurality of mobile devices and transmitting the transactiondata to a financial transaction device in response to verifyingconnection between the vehicle based wallet device and the financialtransaction device by matching the location of the vehicle based walletdevice to a second location associated with the financial institutiondevice. The operations can also include adjusting a vehicle walletbalance associated with the vehicle based wallet device in response toreceiving a notification that the financial transaction device hasprocessed the set of transactions associated with the transaction data,wherein the adjusting the vehicle wallet balance comprises adjusting aset of wallets associated with each of the plurality of mobile devices.

To accomplish the foregoing and related ends, certain illustrativeaspects of the innovation are described herein in connection with thefollowing description and the annexed drawings. These aspects areindicative, however, of but a few of the various ways in which theprinciples of the innovation can be employed and the subject innovationis intended to include all such aspects and their equivalents. Otheradvantages and novel features of the innovation will become apparentfrom the following detailed description of the innovation whenconsidered in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an illustration of an example vehicle based wallet system inaccordance with one or more aspects of the disclosure.

FIG. 2 is an illustration of an example vehicle based wallet system inaccordance with one or more aspects of the disclosure.

FIG. 3 is an illustration of an example flowchart for linking a mobiledevice and mobile wallet to a vehicle based wallet system in accordancewith one or more aspects of the disclosure.

FIG. 4 is an illustration of an example flowchart for verifying a mobiledevice and mobile wallet with a vehicle based wallet system inaccordance with one or more aspects of the disclosure.

FIG. 5 is an illustration of an example flowchart for facilitating afinancial transaction between a vehicle based wallet system and a pointof sale device in accordance with one or more aspects of the disclosure.

FIG. 6 is an illustration of an example flowchart for facilitating afinancial transaction between a vehicle based wallet system and anautomated teller machine in accordance with one or more aspects of thedisclosure.

FIG. 7 is an illustration of an example chart showing a list oftransactions for a vehicle based wallet system according to one or moreembodiments.

FIG. 8 is an illustration of an example flow chart of a method forfacilitating financial transactions with a vehicle based wallet systemaccording to one or more embodiments.

FIG. 9 is an illustration of an example computing environment where oneor more of the provisions set forth herein are implemented, according toone or more embodiments.

FIG. 10 is an illustration of an example computing environment where oneor more of the provisions set forth herein are implemented, according toone or more embodiments.

DETAILED DESCRIPTION

The following terms are used throughout the description, the definitionsof which are provided herein to assist in understanding various aspectsof the disclosure.

As used in this disclosure, the term “device” or “client device” refersto devices, items or elements that may exist in an organization'snetwork, for example, users, groups of users, computer, tablet computer,smart phone, iPad®, iPhone®, wireless access point, wireless client,thin client, applications, services, files, distribution lists,resources, printer, fax machine, copier, scanner, multi-function device,mobile device, badge reader and most any other networked element.

The innovation is now described with reference to the drawings, whereinlike reference numerals are used to refer to like elements throughout.In the following description, for purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the subject innovation. It may be evident, however,that the innovation can be practiced without these specific details. Inother instances, well-known structures and devices are shown in blockdiagram form in order to facilitate describing the innovation.

While specific characteristics are described herein, it is to beunderstood that the features, functions and benefits of the innovationcan employ characteristics that vary from those described herein. Thesealternatives are to be included within the scope of the innovation andclaims appended hereto.

While, for purposes of simplicity of explanation, the one or moremethodologies shown herein, e.g., in the form of a flow chart, are shownand described as a series of acts, it is to be understood andappreciated that the subject innovation is not limited by the order ofacts, as some acts may, in accordance with the innovation, occur in adifferent order and/or concurrently with other acts from that shown anddescribed herein. For example, those skilled in the art will understandand appreciate that a methodology could alternatively be represented asa series of interrelated states or events, such as in a state diagram.Moreover, not all illustrated acts may be required to implement amethodology in accordance with the innovation.

As used in this application, the terms “component” and “system” areintended to refer to a computer-related entity, either hardware, acombination of hardware and software, software, or software inexecution. For example, a component can be, but is not limited to being,a process running on a processor, a processor, an object, an executable,a thread of execution, a program, and/or a computer. By way ofillustration, both an application running on a server and the server canbe a component. One or more components can reside within a processand/or thread of execution, and a component can be localized on onecomputer and/or distributed between two or more computers.

FIG. 1 illustrates an example vehicle based wallet system 100 inaccordance with one or more aspects of the disclosure. In system 100, avehicle based wallet device 108 can facilitates financial transactionsbetween mobile devices 104 and 106 situated in vehicle 102 with afinancial transaction device 110. The financial transaction device 110can be an ATM or POS device, or other device, machine, or system thatcan be used to facilitate financial transactions.

In an embodiment, there can be multiple users in a vehicle that maydesire to perform transactions at a financial transaction device (e.g.,ATM, or POS system such as at a gas station). The users individually caninput their financial and security information into their mobile devices104 and 106 via a graphical user interface (“GUI”) on their mobiledevice and this information can be sent to vehicle wallet 108 which maybe installed on the vehicle's computer. Once the user has inputted theinformation, the device 104 or 106 is verified by the vehicle basedwallet device.

In an embodiment, the device can be verified by the user inputting asecurity code that is displayed on the device 108 or other display inthe vehicle 102 into the mobile device 104 or 106. In other embodiments,the verification can be reversed, by either of the users associated withdevices 104 or 106 entering a security code displayed on their phoneinto a GUI associated with the vehicle based wallet device 108. In otherembodiments, instead of, or in addition to, the security code, the usercan enter into their device the current radio station that the car 102'sradio is currently tuned to. This can be a verification that the usersassociated with devices 104 and 106 are in the vehicle. In yet anotherembodiment, location information can be compared to perform a proximitycheck. The GPS location (or network based location determination or yetother location data associated with the devices 108, 104, and 106) ofthe user device and vehicle can be compared and if they are within apredetermined proximity, the devices 104 and 106 can be verified.

After verification, the financial information from the mobile devices104 and 106 can be sent to the vehicle based wallet device 108 and thisfinancial information can include the deposit or withdrawal informationsuch as the desired transaction amount, whether it's a withdrawal ordeposit, bank account information, routing number, user information, andetc., if the financial transaction device 110 is an ATM (in otherembodiments, the financial transaction device 110 can be a POS machineor other transactional device). The deposit and withdrawal and depositinformation can be compiled into a database in the vehicle wallet device108 that combines the pending transactions from both devices 104 and 106in order to provide the ATM with one transaction. The vehicle walletdevice 108 can connects to the ATM 110 and a security code can be isdisplayed on the ATM 110. To complete the transaction, one of the usersin the vehicle 102 can input the code into a GUI associated with thevehicle 102, vehicle wallet device 108 or one of the mobile devices 104or 106 as a security measure. In addition, the location information ofthe vehicle based wallet 108 can also be compared location informationassociated with the financial transaction device 110 to compare thelocations and only allow the transactions if the locations are within apredetermined distance from each other.

The vehicle based wallet device 108 can send the multiple userstransactions to the ATM 110 in order complete multiple user transactionsat once, the withdrawal amount is combined in order to produce the totalamount for all the users at the ATM 110 and the deposit amount iscombined in order for the ATM 110 to collect the multiple deposits allat once and the appropriate accounts are credited and debited from thetransactions.

If the financial transaction device 110 is a POS machine, the financialinformation is used to transfer the funds to the vehicle based wallet108 so that the vehicle based wallet 108 is holding the funds from theuser. The vehicle 102 or the vehicle based wallet 108 connects to thePOS machine 110 and a security code is displayed on the POS machine 110in which one of the users is required to input the code on a display ofthe vehicle 102 or wallet 108 or alternatively on mobile device 104 or106 as a security measure. Similar location verification can beperformed as above in addition to or in place of the security codeverification. The POS machine 110 sends the required payment amount tothe vehicle wallet 108 and the vehicle wallet 108 sends the fundsthrough a database to the POS machine 110.

In an embodiment, after the financial transaction has been completed,the vehicle based wallet 108 can adjust the balances of the wallets oraccounts associated with each of the mobile device 104 and 106. Forinstance, if deposits into accounts are made during the transactionbetween the vehicle wallet 108 and the ATM 110, the balance of theaccounts associated with device 104 and 106 can be adjusted, or thefunds available in the mobile wallets can be adjusted. Similarly, ifpurchases are made, the vehicle wallet 108 can adjust the fundsavailable to each of the device 104 and 106 based on the relativeproportions of each of the individual transactions.

In an example, if each of the mobile wallets associated with devices 104and 106 have a balance of $100, and the vehicle wallet 108 is used tomake a purchase of $20 of gasoline at a filling station via POS machine110, and the user associated with device 104 contributed $15 towards thepurchase, while the user associated with device 106 contributed $5towards the purchase, the accounts associated with device 104 and 106will be deducted based on their specified contributions, even though asingle transaction of $20 is made at POS machine 110.

Turning now to FIG. 2, illustrated is an example vehicle based walletsystem 200 in accordance with one or more aspects of the disclosure.

The wallet system 200 disclosed in FIG. 2 can include a vehicle basedwallet device 206 that facilitates a set of mobile devices (e.g., mobiledevice 202) making financial transactions with a financial transactiondevice 204 (e.g., ATMs, POS machines, and etc.) The vehicle wallet 206can include a set of communications components 212 that communicate withthe POS device 204 and mobile device 202 via Wi-Fi, Bluetooth, Zig-Bee,3G, 4G, etc. The wallet can also include a GPS component 208 or othercommunications equipment to enable determining location information.Such other equipment can include gyroscope sensors and other movementtracking sensors. In other embodiments, the location can also bedetermined based on network timing based location measurements. A clock214 can be used to measure time and a display 210 can be used fordisplaying security codes, and facilitating the financial transactions.In an embodiment, the display 210 can be interactive and have one ormore methods for providing feedback (e.g., buttons, touch screen, etc).

In an embodiment the vehicle wallet 206 can include vehicle wallet basesoftware which includes the vehicle wallet verification components 226,vehicle wallet data storage software for storing data in the database216, vehicle wallet purchase components 228, and vehicle wallet ATMcomponents 230 to facilitate financial transactions with POS machinesand ATMs respectively. The vehicle wallet 206 also includes the vehicledatabase 216, which includes a vehicle wallet database that storesfinancial information associated with mobile device 202, vehicle walletpending payment database 218, vehicle wallet verification database 220.

The process is initiated with the GUI of mobile device 202 (for whichthere may be multiple user device GUIs 1, 2, . . . N) and the userdevice base software which includes a GUI that allows the user optionssuch as one-time transaction financial data, connected account financialdata, verification inputs, password inputs, receipts and settings. Thedata from the user device GUI selected options is stored in the userdevice database, the GPS location of the vehicle and user device iscompared and if there is a match the user inputs the vehicle code whichis stored in the user device verification database. The user deviceverification database is sent to the vehicle wallet verificationcomponent 226 and if the user device receives the verification approvalthe user device sends the user device database to the vehicle walletdatabase 222.

The financial transaction device 204 connects to the vehicle wallet baseATM component 230 or purchase component 228 if the financial transactiondevice 204 is an ATM or POS machine respectively, and sends thefinancial transaction device 204 GPS location to the respective ATM orPurchase component 228 or 230, the financial transaction device 204sends the financial transaction device 204 security code to the displayof the financial transaction device 204, and the financial transactiondevice 204 receives the vehicle wallet code input. If there is a match,the financial transaction device 204 sends verification approval to thevehicle wallet 206 and receives the vehicle wallet pending transactiondatabase 218 that has a list of the pending transactions. The financialtransaction device 204 then processes the pending transactions withouthaving to finish one transaction and prompt another user to beginanother transaction. In this way the financial transaction device 204has all of the required information to begin the next transactionwithout having to prompt the user allowing the transactions to becompleted in succession to perform a group transaction.

In an embodiment, the vehicle wallet base verification component 226 cancontinuously polling for user devices and sends the vehicle wallet ID tothe user device 202 if scanned. If the user selects verify on the userdevice GUI, the vehicle wallet 206 receives the user device GPSlocation. If the user device GPS location is a match, the vehicle wallet206 sends a match confirmation to the user device 202, and sends thevehicle code to the vehicle display 210, and receives and compares theuser device verification database to the vehicle wallet verificationdatabase 220. If there is a match, the verification component 226 sendsthe verification approval to the user device 202 and receives the userdevice database and stores it in the vehicle wallet database 222.

The database 216 receives the vehicle wallet database from the vehiclewallet base verification component 226 and extracts the transaction typefrom the vehicle wallet database and stores the transactions in thepending transaction database 218. The transactions can then be storeduntil the connection between the financial transaction device 204 andthe vehicle wallet 206 is established.

In the case where the financial transaction device 204 is a POS machine,the vehicle wallet base purchase component 228 receives the vehiclewallet pending transaction database 218 from the database 216 and thepurchase component 228 connects to the point of sale device 204. Thepurchase component 228 compares the GPS locations and if there is amatch the vehicle wallet receives the bill or payment amount from thepoint of sale system 204. If there are sufficient funds in the vehiclewallet pending transaction database 218 and the payment amount isselected to be paid by the vehicle wallet pending transaction database218 the user inputs the payment password, and if there is a match, theuser inputs the point of sale system code from the point of sale system204 display on the vehicle display 210. The user input is sent to thepoint of sale system 204 and if the purchase component 228 receivesverification approval it sends the vehicle wallet pending transactiondatabase 218 to the point of sale system 204.

In the case where the financial transaction device 204 is an ATM, thevehicle wallet base ATM component 230 receives the vehicle walletpending deposit database and vehicle wallet pending withdrawal databasefrom the vehicle wallet pending transaction database 218. The ATMcomponent 230 determine total deposit and determine total withdrawal andstores the total deposit and total withdrawal in the vehicle walletpending transaction database 218. The ATM component 230 connects to theATM and compares the GPS location from the vehicle wallet and the ATM,if there is match the user inputs the ATM password. If the ATM passwordis a match the user inputs the ATM code from the ATM display on to thevehicle display, the user input is sent to the ATM component 230 and ifthe verification approval is received the vehicle wallet sends thevehicle wallet pending transaction database 218 to the ATM component230.

FIGS. 3-6, and 8 illustrates a process in connection with theaforementioned systems. The process in FIGS. 3-6, and 8 can beimplemented for example by systems 100 and 200, illustrated in FIGS. 1-2respectively. While for purposes of simplicity of explanation, themethods are shown and described as a series of blocks, it is to beunderstood and appreciated that the claimed subject matter is notlimited by the order of the blocks, as some blocks may occur indifferent orders and/or concurrently with other blocks from what isdepicted and described herein. Moreover, not all illustrated blocks maybe required to implement the methods described hereinafter

Turning now to FIG. 3, illustrated is an example flowchart 300 forlinking a mobile device and mobile wallet to a vehicle based walletsystem in accordance with one or more aspects of the disclosure. Themethod 300 can start at 302, and a user can input options via a GUIinterface at 304, and at 306, the user GUI options are stored in theuser device database. The communication channels are initiated at 308and the user device connects to the vehicle wallet at 310. The userdevice receives the vehicle wallet ID at 312, and the user selects“verify” on the user device GUI at 314.

The user device sends the GPS location to the vehicle wallet at 316, ifthere is no match confirmation received then the process ends at 318,but if the match confirmation is received at 318 the user inputs thevehicle code at 320. The vehicle code input is stored in the user deviceverification database at 322. The user device receives a request for theuser device verification database from the vehicle wallet base softwareverification software at 324 and the user device sends the user deviceverification database to the vehicle wallet base software verificationsoftware at 326. If the verification approval is not received at 328 theuser device sends a request for a new code at 332 and receives a newcode from the vehicle wallet base software verification software at 334and the process returns to the user inputting the vehicle code at 320.If the verification approval is received at 328 the user device sendsthe user device database to the vehicle wallet at 330.

Turning now to FIG. 4, illustrated is an illustration of an exampleflowchart 400 for verifying a mobile device and mobile wallet with avehicle based wallet system in accordance with one or more aspects ofthe disclosure. The method 400 can start at 402 with the initiating thecommunication channels at 404 and continuously polling at 406 until auser device is available. Once a user device is available theverification software sends the vehicle wallet ID to the user device at408, if the user does not select verify on the user device at 410 theprocess ends, but if the user does select verify on the user device GUIat 410 the verification software will receive the GPS location from theuser device at 412. If the GPS location is not a match at 414 then theprocess ends but if there is a match at 414 the verification softwaresends a match confirmation at 416 to the user device and sends thevehicle code to the vehicle display at 418.

The verification software sends a request for user device verificationdatabase at 420 and receives the user device verification database at422 which is then compared to the vehicle wallet verification databaseat 424. If the user device verification database and vehicle walletverification database do not match at 426 the verification softwaredetermines if there is a request for a new code at 428, if there is theverification software sends the vehicle code to the vehicle display at430, if there is no request for a new code then the process ends. If theuser device verification database and vehicle wallet verificationdatabase do match the verification software sends the verificationapproval and receives the user device database from the user device basesoftware at 432, the user device database is stored in the vehiclewallet database at 434 and the vehicle wallet database is sent to thevehicle wallet base software data storage software at 436.

Turning now to FIG. 5, illustrated is an example flowchart 500 forfacilitating a financial transaction between a vehicle based walletsystem and a point of sale device in accordance with one or more aspectsof the disclosure. Method 500 can start at 502 where the purchasesoftware receives the vehicle wallet pending payment database from thevehicle wallet base software data storage software. The communicationchannels are initiated at 504 and if the point of sale system isavailable at 506, the purchase software connects to the point of salesystem at 508, if the point of sale system is not available at 506, thenthe process returns to receiving the vehicle wallet pending paymentdatabase. The purchase software receives the GPS location of the pointof sale system at 510 and compares it to the vehicle GPS location at512, if it is not a match at 514 then the process ends, but if there isa match the purchase software receives the payment amount from the pointof sale system at 516.

If there are not sufficient funds at 518 in the vehicle wallet pendingpayment database then insufficient funds is reported to the user at 536.If there are sufficient funds in the vehicle wallet pending paymentdatabase at 518, the user determines whether or not to pay the amountwith the vehicle wallet pending payment database at 520. If the userselects no at 520 then the payment method is cancelled, at 526 but ifthe user selects yes at 520 the user inputs the payment password at 522.If the payment password is not a match at 524 then the payment method iscancelled, but if it is a match at 524 the user inputs the point of salesystem code from the point of sale system display on the vehicle displayat 528. The user input is sent to the point of sale base software at 520and if the verification approval is not received at 532 then the processends, but if the verification approval is received at 532 then thepurchase software sends the vehicle wallet pending payment database tothe point of sale system software at 534.

Turning now to FIG. 6, illustrated is an example flowchart 600 forfacilitating a financial transaction between a vehicle based walletsystem and an automated teller machine in accordance with one or moreaspects of the disclosure. The method 600 can start at 602 and 604 wherethe ATM software receives the vehicle wallet pending deposit databaseand at vehicle wallet pending withdrawal database from the vehiclewallet base software data storage software. The vehicle wallet basesoftware ATM software determines the total deposit at 606 and totalwithdrawal at 608 and the total deposit and total withdrawal is storedin the vehicle wallet ATM database at 610. The communication channelsare initiated at 612 and if the ATM is not available at 614 the processends, if the ATM is available the ATM software connects to the ATM at616, receives the GPS location of the ATM at 618, and compares it to theGPS location of the vehicle at 620.

If the GPS location is not a match at 622 the process ends, but if theGPS location is a match at 622 the user inputs the ATM password on thevehicle display at 624. If the ATM password is not a match at 626 theprocess ends, but if it is a match the user inputs the ATM code from theATM display on to the vehicle display at 628. The user input is sent tothe ATM base software at 630 and if the verification approval is notreceived at 632 the process ends and if the verification approval isreceived the vehicle wallet sends the vehicle wallet ATM database to theATM base software at 634.

Turning now to FIG. 7, illustrated in 700 are example charts showing alist of transactions for a vehicle based wallet system according to oneor more embodiments. Chart 702 shows a consolidated list of pendingtransactions, both withdrawals and deposits from an ATM and a pendingpurchases from a POS device. Chart 702 can show the pending transactionsstored in the pending transaction database 218 shown in FIG. 2 as anexample. The pending transaction database can store the time and date atwhich the transactions are logged or entered. The database can also showthe User ID associated with each transaction for correct attribution,and the type of transaction. The transaction database can also store thesource or destination of the transaction as well as info (financialinformation), amount, status, and total.

The chart 704 also displays the vehicle wallet verification databasewhich includes the user ID, code, verified (which is if the code isverified), and new code (which would be if a new code was requested). Anexample data entry is the user ID is JS1234, the code is VFRD34, thecode is verified and no new code was requested.

The vehicle wallet verification database shown in 704 is used todetermine if the user inputs the same verification code that isdisplayed on the vehicle display in order to allow the user device totransfer data with the vehicle wallet. The vehicle wallet verificationdatabase is compared to the user device verification database in thevehicle wallet base software verification software, if there is no matchthe software determines if a new code has been requested, if there is amatch the software sends verification approval to the user device.

Turning now to FIG. 8, illustrated an example flow chart of a method 800for facilitating financial transactions with a vehicle based walletsystem according to one or more embodiments.

Method 800 can start at 802 where the method includes registering, by adevice comprising a processor, a set of mobile wallets with a vehiclebased wallet, wherein the registering comprises collecting financialaccount data and security data associated with the set of mobilewallets, and wherein the set of mobile wallets are associated with a setof corresponding mobile devices.

At 804 the method includes verifying the set of mobile wallets bymatching a location of the set of mobile devices to a location of the ofthe vehicle based wallet. At 806, the method includes collectingtransaction data associated with a set of transactions from the mobilewallets. At 808, the method includes transmitting the transaction datato a financial transaction device.

At 810, the method includes adjusting a balance of the vehicle basedwallet in response to receiving a notification that the financialtransaction device has processed the set of transactions associated withthe transaction data.

Referring now to FIG. 9, there is illustrated a block diagram of acomputer operable to execute the disclosed architecture. In order toprovide additional context for various aspects of the subjectinnovation, FIG. 9 and the following discussion are intended to providea brief, general description of a suitable computing environment 900 inwhich the various aspects of the innovation can be implemented. Whilethe innovation has been described above in the general context ofcomputer-executable instructions that may run on one or more computers,those skilled in the art will recognize that the innovation also can beimplemented in combination with other program modules or componentsand/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, the inventive methods can be practicedwith other computer system configurations, including single-processor ormultiprocessor computer systems, minicomputers, mainframe computers, aswell as personal computers, hand-held computing devices,microprocessor-based or programmable consumer electronics, and the like,each of which can be operatively coupled to one or more associateddevices.

The illustrated aspects of the innovation may also be practiced indistributed computing environments where certain tasks are performed byremote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

A computer typically includes a variety of computer-readable media.Computer-readable media can be any available media that can be accessedby the computer and includes both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media includes volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information such as computer-readableinstructions, data structures, program modules or other data. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disk (DVD)or other optical disk storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to store the desired information and which canbe accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media.

With reference again to FIG. 9, the exemplary environment 900 forimplementing various aspects of the innovation includes a computer 902,the computer 902 including a processing unit 904, a system memory 906and a system bus 908. The system bus 908 couples system componentsincluding, but not limited to, the system memory 906 to the processingunit 904. The processing unit 904 can be any of various commerciallyavailable processors. Dual microprocessors and other multi-processorarchitectures may also be employed as the processing unit 904.

The system bus 908 can be any of several types of bus structure that mayfurther interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 906 includesread-only memory (ROM) 910 and random access memory (RAM) 912. A basicinput/output system (BIOS) is stored in a non-volatile memory 910 suchas ROM, EPROM, EEPROM, which BIOS contains the basic routines that helpto transfer information between elements within the computer 902, suchas during start-up. The RAM 912 can also include a high-speed RAM suchas static RAM for caching data.

The computer 902 further includes an internal hard disk drive (HDD) 914(e.g., EIDE, SATA), which internal hard disk drive 914 may also beconfigured for external use in a suitable chassis (not shown), amagnetic floppy disk drive (FDD) 916, (e.g., to read from or write to aremovable diskette 918) and an optical disk drive 920, (e.g., reading aCD-ROM disk 922 or, to read from or write to other high capacity opticalmedia such as the DVD). The hard disk drive 914, magnetic disk drive 916and optical disk drive 920 can be connected to the system bus 908 by ahard disk drive interface 924, a magnetic disk drive interface 926 andan optical drive interface 928, respectively. The interface 924 forexternal drive implementations includes at least one or both ofUniversal Serial Bus (USB) and IEEE 1394 interface technologies. Otherexternal drive connection technologies are within contemplation of thesubject innovation.

The drives and their associated computer-readable media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 902, the drives and mediaaccommodate the storage of any data in a suitable digital format.Although the description of computer-readable media above refers to aHDD, a removable magnetic diskette, and a removable optical media suchas a CD or DVD, other types of media which are readable by a computer,such as zip drives, magnetic cassettes, flash memory cards, cartridges,and the like, may also be used in the exemplary operating environment,and further, that any such media may contain computer-executableinstructions for performing the methods of the innovation.

A number of program modules can be stored in the drives and RAM 912,including an operating system 930, one or more application programs 932,other program modules 934 and program data 936. All or portions of theoperating system, applications, modules, and/or data can also be cachedin the RAM 912. The innovation can be implemented with variouscommercially available operating systems or combinations of operatingsystems.

A user can enter commands and information into the computer 902 throughone or more wired/wireless input devices, e.g., a keyboard 938 and apointing device, such as a mouse 940. Other input devices (not shown)may include a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, or the like. These and other input devicesare often connected to the processing unit 904 through an input deviceinterface 942 that is coupled to the system bus 908, but can beconnected by other interfaces, such as a parallel port, an IEEE 1394serial port, a game port, a USB port, an IR interface, etc.

A monitor 944 or other type of display device is also connected to thesystem bus 908 via an interface, such as a video adapter 946. Inaddition to the monitor 944, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 902 may operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 948. The remotecomputer(s) 948 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer902, although, for purposes of brevity, only a memory/storage device 950is illustrated. The logical connections depicted include wired/wirelessconnectivity to a local area network (LAN) 952 and/or larger networks,e.g., a wide area network (WAN) 954. Such LAN and WAN networkingenvironments are commonplace in offices and companies, and facilitateenterprise-wide computer networks, such as intranets, all of which mayconnect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer 902 is connectedto the local network 952 through a wired and/or wireless communicationnetwork interface or adapter 956. The adapter 956 may facilitate wiredor wireless communication to the LAN 952, which may also include awireless access point disposed thereon for communicating with thewireless adapter 956.

When used in a WAN networking environment, the computer 902 can includea modem 958, or is connected to a communications server on the WAN 954,or has other means for establishing communications over the WAN 954,such as by way of the Internet. The modem 958, which can be internal orexternal and a wired or wireless device, is connected to the system bus908 via the serial port interface 942. In a networked environment,program modules or components depicted relative to the computer 902, orportions thereof, can be stored in the remote memory/storage device 950.The network connections shown are exemplary and other means ofestablishing a communications link between the computers can be used.

The computer 902 is operable to communicate with any wireless devices orentities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. Wi-Fi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out; anywhere within the range of a basestation. Wi-Fi networks use radio technologies called IEEE 802.11 (a, b,g, n, etc.) to provide secure, reliable, fast wireless connectivity. AWi-Fi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE 802.3 or Ethernet).Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands, atan 11 Mbps (802.11a) or 54 Mbps (802.11b) data rate, for example, orwith products that contain both bands (dual band), so the networks canprovide real-world performance similar to wired Ethernet networks usedin many offices.

Referring now to FIG. 10, there is illustrated a schematic block diagramof an exemplary computing environment 1000 in accordance with thesubject innovation. The system 1000 includes one or more client(s) 1002.The client(s) 1002 can be hardware and/or software (e.g., threads,processes, computing devices).

The system 1000 also includes one or more server(s) 1004. The server(s)1004 can also be hardware and/or software (e.g., threads, processes,computing devices). The servers 1004 can house threads to performtransformations by employing the innovation, for example. One possiblecommunication between a client 1002 and a server 1004 can be in the formof a data packet adapted to be transmitted between two or more computerprocesses. The system 1000 includes a communication framework 1006(e.g., a global communication network such as the Internet) that can beemployed to facilitate communications between the client(s) 1002 and theserver(s) 1004.

Communications can be facilitated via a wired (including optical fiber)and/or wireless technology. The client(s) 1002 are operatively connectedto one or more client data store(s) 1008 that can be employed to storeinformation local to the client(s) 1002. Similarly, the server(s) 1004are operatively connected to one or more server data store(s) 1010 thatcan be employed to store information local to the servers 1004.

What has been described above includes examples of the innovation. Itis, of course, not possible to describe every conceivable combination ofcomponents or methodologies for purposes of describing the subjectinnovation, but one of ordinary skill in the art may recognize that manyfurther combinations and permutations of the innovation are possible.Accordingly, the innovation is intended to embrace all such alterations,modifications and variations that fall within the spirit and scope ofthe appended claims. Furthermore, to the extent that the term “includes”is used in either the detailed description or the claims, such term isintended to be inclusive in a manner similar to the term “comprising” as“comprising” is interpreted when employed as a transitional word in aclaim.

The invention claimed is:
 1. A vehicle based wallet system, comprising:a memory to store computer-executable instructions; and a processor,coupled to the memory, to facilitate execution of thecomputer-executable instructions to perform operations, comprising:receiving wallet registration data from a plurality of mobile devices,wherein the wallet registration data includes financial account data andsecurity data; verifying the wallet registration data for the pluralityof mobile devices; compiling transaction data associated with a set oftransactions from the plurality of mobile devices; transmitting thetransaction data to a financial transaction device; and adjusting avehicle wallet balance in response to receiving a notification that thefinancial transaction device has processed the set of transactionsassociated with the transaction data, wherein adjusting the vehiclewallet balance comprises adjusting a set of wallets associated with eachof the plurality of mobile devices, wherein the financial transactiondevice processes pending transactions without having to finish atransaction presently being executed and simultaneously prompts users tobegin additional transactions.
 2. The vehicle based wallet system ofclaim 1, wherein the operations further comprise: verifying a connectionbetween the vehicle based wallet system and the financial transactiondevice.
 3. The vehicle based wallet system of claim 2, wherein theverifying the connection between the vehicle based wallet system and thefinancial transaction device comprises matching a location of a vehicleassociated with the vehicle based wallet system to another locationassociated with the financial transaction device.
 4. The vehicle basedwallet system of claim 2, wherein the verifying the connection betweenthe vehicle based wallet system and the financial transaction devicecomprises verifying that a code received via a graphical user interfacematches a code received via the financial transaction device.
 5. Thevehicle based wallet system of claim 1, wherein the verifying the walletregistration data for the plurality of mobile devices comprises matchinga location of a vehicle associated with the vehicle based wallet systemto locations associated with the plurality of mobile devices.
 6. Thevehicle based wallet system of claim 1, wherein the transmitting thetransaction data to the financial transaction device via at least one ofa Wi-Fi connection, a Bluetooth connection, a near field connection, acellular connection, or a Zigbee connection.
 7. The vehicle based walletsystem of claim 1, wherein the financial transaction device is anautomated telling machine, and the set of transactions are at least oneof account withdrawals or account deposits.
 8. The vehicle based walletsystem of claim 7, wherein the operations further comprise:proportioning the account withdrawal or the account deposit betweenwallets associated with the plurality of mobile device according to apredetermined criterion.
 9. The vehicle based wallet system of claim 8,wherein the predetermined criterion is based on the transaction dataassociated with the set of transactions.
 10. The vehicle based walletsystem of claim 1, wherein the financial transaction device is a pointof sale device, and the set of transactions are purchase transactions.11. The vehicle based wallet system of claim 10, wherein the set oftransactions collectively result in a single transaction with the pointof sale device.
 12. A method, comprising: registering, by a devicecomprising a processor, a set of mobile wallets with a vehicle basedwallet, wherein the registering comprises collecting financial accountdata and security data associated with the set of mobile wallets, andwherein the set of mobile wallets are associated with a set ofcorresponding mobile devices; verifying the set of mobile wallets bymatching a location of the set of mobile devices to a location of the ofthe vehicle based wallet; collecting transaction data associated with aset of transactions from the mobile wallets; transmitting thetransaction data to a financial transaction device, wherein thefinancial transaction device is an automatic teller machine (ATM) or apoint of sale (POS) system; adjusting a balance of the vehicle basedwallet in response to receiving a notification that the financialtransaction device has processed the set of transactions associated withthe transaction data; and adjusting a balance of the set of mobilewallets in response to adjusting the balance of the vehicle basedwallet, wherein the set of mobile wallets are adjusted proportionallybased on a predetermined arrangement between the mobile wallets, whereintransactions take the form of point of sale transactions and ATMdeposits and withdrawals, wherein the vehicle based wallet can send thetransactions of multiple users to a single financial transaction devicein order to complete multiple user transactions at once.
 13. The methodof claim 12, further comprising: verifying a connection between thevehicle based wallet system and the financial transaction device. 14.The method of claim 13, wherein the verifying the connection between thevehicle based wallet system and the financial transaction devicecomprises matching a location of a vehicle associated with the vehiclebased wallet system to another location associated with the financialtransaction device.
 15. The method of claim 12, wherein adjusting thebalance of the set of mobile wallets further comprises at least one ofcrediting or debiting the balance of the set of mobile wallets based onthe type of transaction.
 16. The method of claim 13, wherein theverifying the connection between the vehicle based wallet system and thefinancial transaction device comprises verifying that a code receivedvia a graphical user interface matches a code received via the financialtransaction device.
 17. A non-transitory computer-readable storagedevice configured to store instructions, that when executed by aprocessor perform operations, comprising: receiving wallet registrationdata from a plurality of mobile devices, wherein the wallet registrationdata includes financial account data and security data; verifying thewallet registration data for the plurality of mobile devices by matchinglocations associated with the plurality of mobile devices to a locationassociated with a vehicle based wallet device; compiling transactiondata associated with a set of transactions from the plurality of mobiledevices; transmitting the transaction data to a financial transactiondevice in response to verifying connection between the vehicle basedwallet device and the financial transaction device by matching thelocation of the vehicle based wallet device to a second locationassociated with the financial institution device; and adjusting avehicle wallet balance associated with the vehicle based wallet devicein response to receiving a notification that the financial transactiondevice has processed the set of transactions associated with thetransaction data, wherein adjusting the vehicle wallet balance comprisesadjusting a set of wallets associated with each of the plurality ofmobile devices, wherein the financial transaction device processespending transactions without having to finish a transaction presentlybeing executed and simultaneously prompts users to begin additionaltransactions.
 18. The non-transitory computer-readable storage device ofclaim 17, wherein the financial institution device is at least one of anautomated teller machine device or a point of sale device.
 19. Thenon-transitory computer-readable storage device of claim 17, whereinverifying the connection between the vehicle based wallet device and thefinancial transaction device comprises verifying that a code receivedvia a graphical user interface on the vehicle based wallet devicematches a code received via the financial transaction device.
 20. Themethod of claim 12, wherein verifying the set of mobile wallets bymatching a location of the set of mobile devices to a location of the ofthe vehicle based wallet is accomplished using GPS.